[next] Ensure root-most index GSP page is located correctly #5309
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes root-most index GSP pages not being located correctly, this also uncovered the initial revalidate value not being stored to the
prerender-manifest
correctly causing an incorrectPrerender
output to be built which is fixed in vercel/next.js#18053Note: tests won't pass until the above mentioned Next.js PR is landed to canary
x-ref: vercel/next.js#17370